Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

Former Site Of Kingsway House

reference: TPO7215
name: Former Site Of Kingsway House
tree-preservation-order: undefined
Lloyds Avenue 2011
uprn
address-text
point: POINT (-0.655011 53.578219)
geometry: MULTIPOLYGON (((-0.654996 53.578219,-0.654998 53.578223,-0.655003 53.578227,-0.655011 53.578228,-0.655018 53.578227,-0.655024 53.578223,-0.655026 53.578219,-0.655024 53.578214,-0.655019 53.578211,-0.655011 53.578210,-0.655004 53.578211,-0.654998 53.578214,-0.654996 53.578219)))
notes
felled-date
entry-date: 2011-10-11
start-date: 2011-09-04
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve North Lincolnshire Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL